Splitting parser feature into multiple subfeatures to reduce dependency bloat #9546
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
GNU testsuite comparison: |
ChrisDryden
force-pushed
the
parser_features
branch
from
195a205 to
db820a3
Compare
|
GNU testsuite comparison: |
ChrisDryden
force-pushed
the
parser_features
branch
from
db820a3 to
f908468
Compare
|
GNU testsuite comparison: |
Contributor
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Working on investigating the dependencies of each of the sub packages to see if there's any quick wins to split the features. The procfs is the main dependency bottleneck when compiling most binaries and removing it from the main parser feature will make things much faster to compile.
This basically removes around 20 dependencies from each binary that uses the parser